<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>88. System Analysis</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="SYSTEM_ANALYSIS">SYSTEM ANALYSIS</h1>
		<h3 id="DEFINITION">DEFINITION</h3>
		<p>The System Analysis phase focuses on the System/Software itself, in order to define how it can satisfy the former Operational need, along with its expected behavior and qualities: system/software Functions to be supported, related Exchanges, non functional constraints (safety, security&hellip;), performances allocated to system boundary, role sharing and interactions between System and Operators.</p>
		<p>Outputs of System Analysis mainly consist of system/software functional need description, interoperability and interaction with the users and external Systems (functions, exchanges plus non-functional constraints, external interfaces), and System/Software requirements.</p>
		<h3 id="ICONS">ICONS</h3>
		<p>
			<img height="66" width="75" border="0" src="Images/88.%20System%20Analysis_html_m5da03533.png"/>
		</p>
	</body>
</html>